Skip to content

Conversation

@Maverobot
Copy link
Contributor

Description

LifecycleNode is missing a get_parameter_or public function, which exists in Node.

Is this user-facing behavior change?

Yes. It makes the behavior of LifecycleNode more consistent with Node.

Did you use Generative AI?

No.

@Maverobot Maverobot force-pushed the add-get-parameter-or-for-lifecyclenode branch from f7aa101 to 8ffcf53 Compare October 31, 2025 20:01
Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that is just fine to have this methods in LifecycleNode to keep the consistency with Node under current design.

can you also add the test to make sure this method works?

@Maverobot
Copy link
Contributor Author

Adding tests makes total sense. A new test has now been pushed in a separate commit.

@fujitatomoya
Copy link
Collaborator

Pulls: #2973
Gist: https://gist.githubusercontent.com/fujitatomoya/26fc70fefbda7756e0caafb9c303746c/raw/dc036209abea296077557d87bdd632b872200090/ros2.repos
BUILD args: --packages-above-and-dependencies rclcpp_lifecycle
TEST args: --packages-above rclcpp_lifecycle
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/17410

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@ahcorde ahcorde merged commit eb49444 into ros2:rolling Nov 7, 2025
3 checks passed
@Maverobot Maverobot deleted the add-get-parameter-or-for-lifecyclenode branch November 7, 2025 11:39
@ahcorde
Copy link
Contributor

ahcorde commented Nov 7, 2025

@fujitatomoya do we need to backport this one ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants